Methods, Systems, and Products for Providing Ring Backs

ABSTRACT

Methods, systems, and products are disclosed for providing a ring back to a calling party&#39;s communications device. A first call is placed to a called number. An identification sequence is received during the first call. When the first call ends, a second call is placed to a server. The identification sequence is sent to the server during the second call, and the ring back associated with the identification sequence is received. The ring back is stored in memory of the calling party&#39;s communications device and retrieved when subsequent calls are made to the called number. The ring back is then presented on the calling party&#39;s communications device to indicate the called number is ringing.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.12/254,286, filed Oct. 20, 2008, now issued as U.S. Pat. No. ______, andincorporated herein by reference in its entirety.

BACKGROUND

Exemplary embodiments generally relate to telephonic communications andto telecommunications and, more particularly, to supervisory controlline signaling, to special services and programming control in aradiotelephone system, and to transceiver call alerting.

Personalized phones are very popular. Mobile phones, for example, can bepersonalized with selected ring tones, colorful and themed covers, andeven more unique phone designs. Recently customers can even downloadsongs and other ring tones to further personalize their phones.Customers desire these personalized features, and these personalizedfeatures are profitable for the service provider. Service providers andcustomers thus benefit from an ever expanding selection of personalizedfeatures.

BRIEF SUMMARY OF THE INVENTION

Exemplary embodiments provide methods, systems, apparatuses, andproducts for a ring back service. This ring back service may bepersonalized by a subscriber, and this ring back service provides anadditional revenue opportunity for the service provider. This ring backservice provides a customizable alert to a calling party, and thiscustomizable alert means the called party's communications device isringing, vibrating, or otherwise alerting to an incoming telephone call,email, or other communication. As most people know, when a telephonecall is placed, the calling party hears a “ring back” tone. This ringback tone indicates the called party's terminal is ringing, or otherwisealerting, to the incoming call.

Exemplary embodiments include a method of providing a personalized ringback. A first call is placed to a called number. An identificationsequence is received during the first call. A second call is placed to aserver when the first call is completed. An identification sequence issent to the server during the second call. The personalized ring back isreceived during the second call and stored. When subsequent calls aremade to the called number, the personalized ring back is retrieved frommemory and presented to the calling party.

Other exemplary embodiments include a processor-controlled device thatprovides a ring back. The processor-controlled device is operative toplace a first call to a called number. An identification sequence isreceived during the first call. A second call is placed to a server whenthe first call is completed. An identification sequence is sent to theserver during the second call. The personalized ring back is receivedduring the second call and stored. When subsequent calls are made to thecalled number, the personalized ring back is retrieved from memory andpresented to the calling party.

More exemplary embodiments describe a computer readable storage mediumthat stores processor-executable instructions for performing a method ofproviding a ring back to a calling party's communications device. Afirst call is placed to a called number. An identification sequence isreceived during the first call. A second call is placed to a server whenthe first call is completed. An identification sequence is sent to theserver during the second call. The personalized ring back is receivedduring the second call and stored. When subsequent calls are made to thecalled number, the personalized ring back is retrieved from memory andpresented to the calling party.

Other systems, methods, and/or computer program products according tothe exemplary embodiments will be or become apparent to one withordinary skill in the art upon review of the following drawings anddetailed description. It is intended that all such additional systems,methods, and/or computer program products be included within thisdescription, be within the scope of the claims, and be protected by theaccompanying claims.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

These and other features, aspects, and advantages of the exemplaryembodiments are better understood when the following DetailedDescription is read with reference to the accompanying drawings,wherein:

FIG. 1 is a simplified schematic illustrating a ring back service,according to exemplary embodiments;

FIGS. 2-5 are more detailed schematics illustrating the ring backservice, according to more exemplary embodiments;

FIGS. 6-7 are schematics illustrating a telephony ring back, accordingto exemplary embodiments;

FIG. 8 illustrates another operating environment, according to exemplaryembodiments;

FIGS. 9-11 are schematics illustrating various communications devicesfor presenting ring backs, according to exemplary embodiments;

FIGS. 12-14 are schematics further illustrating various communicationsdevices for presenting ring backs, according to exemplary embodiments;

FIG. 15 is another schematic further illustrating various communicationsdevices for presenting ring backs, according to exemplary embodiments;

FIG. 16 is another schematic illustrating this ring back service,according to exemplary embodiments;

FIG. 17 is a schematic illustrating a network-centric ring back service,according to exemplary embodiments; and

FIGS. 18 and 19 are flowcharts illustrating methods of providing thepersonalized ring back, according to exemplary embodiments.

DETAILED DESCRIPTION

The exemplary embodiments will now be described more fully hereinafterwith reference to the accompanying drawings. The exemplary embodimentsmay, however, be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein. Theseembodiments are provided so that this disclosure will be thorough andcomplete and will fully convey the exemplary embodiments to those ofordinary skill in the art. Moreover, all statements herein recitingembodiments, as well as specific examples thereof, are intended toencompass both structural and functional equivalents thereof.Additionally, it is intended that such equivalents include bothcurrently known equivalents as well as equivalents developed in thefuture (i.e., any elements developed that perform the same function,regardless of structure).

Thus, for example, it will be appreciated by those of ordinary skill inthe art that the diagrams, schematics, illustrations, and the likerepresent conceptual views or processes illustrating the exemplaryembodiments. Those of ordinary skill in the art further understand thatthe exemplary hardware, software, processes, methods, and/or operatingsystems described herein are for illustrative purposes and, thus, arenot intended to be limited to any particular named manufacturer.

As used herein, the singular forms “a,” “an,” and “the” are intended toinclude the plural forms as well, unless expressly stated otherwise. Itwill be further understood that the terms “includes,” “comprises,”“including,” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or groups thereof. It will be understood thatwhen an element is referred to as being “connected” or “coupled” toanother element, it can be directly connected or coupled to the otherelement or intervening elements may be present. Furthermore, “connected”or “coupled” as used herein may include wirelessly connected or coupled.As used herein, the term “and/or” includes any and all combinations ofone or more of the associated listed items.

It will also be understood that, although the terms first, second, etc.may be used herein to describe various elements, these elements shouldnot be limited by these terms. These terms are only used to distinguishone element from another. For example, a first device could be termed asecond device, and, similarly, a second device could be termed a firstdevice without departing from the teachings of the disclosure.

FIG. 1 is a simplified schematic illustrating a ring back service,according to exemplary embodiments. A calling party, using the callingparty's communications device 10, initiates a communication 12 to acalled party's communications device 14. The communication 12 may be anyform of electronic communication (such as an email, instant message,page, or facsimile communication), a Plain Old Telephone Systemtelephone call, and/or an Internet Protocol telephone call. Thecommunication 12 routes from the calling party's communications device10 to the called party's communications device 14 via a communicationsnetwork 16. When the communication 12 is received, the called party'scommunications device 14 may ring, vibrate, flash, buzz, or otherwisealert to the incoming communication 12.

The calling party's communications device 10 also alerts. The callingparty sees/hears/feels a ring back 18. This ring back 18 alerts thecalling party that the called party's communications device 14 isringing, vibrating, or otherwise alerting of the incoming communication12. That is, when the calling party sees/hears the ring back 18, thecalling party recognizes that the called party's communications device14 is ringing.

Exemplary embodiments, however, allow the called party to specify thering back 18. If the called party and/or the calling party subscribes tothis ring back service, the called party may select the ring back 18that is presented to the calling party. When the calling partysees/hears the ring back 18, that ring back 18 is personalized by thecalled party subscriber. The ring back 18 may be any music, tone(s),and/or graphics selected by the called party. The called party, forexample, may select an .mp3 file to be presented to the calling party.The calling party might also view a picture, portions of a movie, orother graphics. The called party might even select personal pictures,self-composed music, or other content. The called party subscriber couldeven specify streamed audio and/or video content, such as radio, stockquotes, news, weather, and/or advertisements. The called party couldalso use logical rules for specifying ring backs. These logical rulesmight specify ring backs by the month, the day of the week, and/or thetime of day. As further explained herein, the called party subscribermay even associate particular ring backs to particular calling parties,thus providing a variety of personalized ring backs.

FIGS. 2-5 are more detailed schematics illustrating the ring backservice, according to more exemplary embodiments. When the communication12 is received, the called party's communications device 14 rings,vibrates, and/or otherwise alerts to the incoming communication 12. Thecalling party's communications device 10, however, may also alert. AsFIG. 2 illustrates, the called party's communications device 14 maystore a ring back module 30 in memory 32, and a processor 34communicates with the memory 32 to execute the ring back module 30. Thering back module 30 may be a set of processor executable instructionsthat control or manage the ring back service for the called party.

The calling party's communications device 10 may also execute the ringback module 30. The calling party's communications device 10 may storethe ring back module 30 in memory 36 of the calling party'scommunications device 10. A processor 38 may communicate with the memory36 and execute the ring back module 30. The ring back module 30 maysimilarly control or manage the ring back service for the calling party.The ring back module 30 may comprise methods, computer programs, and/orcomputer program products that help provide the ring back 18 at thecalling party's communications device 10.

FIG. 2 also illustrates a communications server 40. The communicationsserver 40 operates at any location within the communications network 16.The communications server 40 may store and execute a server-side ringback module 42. Although not shown for simplicity, the server-side ringback module 42 may be stored in the memory of the communications server40. A processor may communicate with the server's memory and execute theserver-side ring back module 42. The ring back module 30 and theserver-side ring back module 42 may cooperate to provide the ring back18 at the calling party's communications device 10.

Personalized ring backs are provided to the calling party. As thecommunication 12 is communicated to the called party's communicationsdevice 14, exemplary embodiments determine if the personalized ring backservice is required. If the personalized ring back 18 is required, thering back module 30 and/or the server-side ring back module 42 maycooperate to provide the personalized ring back 18, as the followingparagraphs will explain. The personalized ring back 18 is presented atthe calling party's communications device 10 to alert that the calledparty's communications device 14 is ringing, vibrating, or otherwisealerting of the incoming communication 12.

FIG. 3 continues illustrating the ring back service, according toexemplary embodiments. When the calling party's communications device 10initiates or sends the communication 12 to the called party'scommunications device 14, the communication 12 routes to acommunications address 50 associated with the called party'scommunications device 14. If the communication 12 is an email orVoice-over Internet Protocol call, for example, then the communication12 may route to an Internet Protocol address 52 associated with thecalled party's communications device 14. If the communication 12 is atelephone call or Voice-over Internet Protocol call, then thecommunication 12 may route to a called telephone number 54 associatedwith the called party's communications device 14.

The calling party's communications device 10 may then receive or producea default ring back 56. The default ring back 56 is a standard orgeneric ring back to indicate that the called party's communicationsdevice 14 is alerting of the incoming communication 12. The default ringback 56 may originate from the called party's communications device 14and/or from the communications server 40. When the called party'scommunications device 14 receives, detects, or is informed of theincoming communication 12, for example, the ring back module 30(operating in the called party's communications device 14) may retrievethe default ring back 56 from the memory 32 of the called party'scommunications device 14. The ring back module 30 then causes theprocessor 34 to send the default ring back 56 to the calling party'scommunications device 10. The default ring back 56, for example, mayroute or communicate to a communications address (e.g., an InternetProtocol address 58 or calling telephone number 60) associated with thecalling party's communications device 10. The communications server 40,likewise, may send the default ring back 56 to the calling party'scommunications device 10. When the server-side ring back module 42receives, detects, or is notified of the incoming communication 12, theserver-side ring back module 42 may retrieve the default ring back 56from memory and send the default ring back 56 to the communicationsaddress associated with the calling party's communications device 10.The default ring back 56, alternatively or additionally, may be locallyretrieved from the memory 36 of the calling party's communicationsdevice 10.

Regardless, the default ring back 56 may comprise an identificationsequence 70. When the calling party's communications device 10 receivesthe default ring back 56, ring back module 30 instructs the processor 38to inspect the default ring back 56 for the identification sequence 70.The ring back module 30 causes the calling party's communications device10 to audibly and/or visually present the default ring back 56. The ringback module 30 also causes the processor 38 to store the identificationsequence 70 in the memory 36 of the calling party's communicationsdevice 10.

FIG. 4 illustrates retrieval of the personalized ring back 18, accordingto exemplary embodiments. After the identification sequence 70 isreceived, the calling party's communications device 10 may then contactthe communications server 40. The ring back module 30 may cause thecalling party's communications device 10 to send the identificationsequence 70 to the communications server 40. The calling party'scommunications device 10, for example, may send a ring back request 72to the communications server 40, and the ring back request 72 maycomprise the identification sequence 70. The ring back request 72 mayalso comprise the Internet Protocol address 58 and/or the telephonenumber 60 associated with the calling party's communications device 10.When the communications server 40 receives the ring back request 72, theserver-side ring back module 42 acquires the identification sequence 70.The server-side ring back module 42 then instructs the server'sprocessor to query a ring back database 74 for the identificationsequence 70. The ring back database 74 is illustrated as being locallystored in the communications server 40, but the ring back database 74may be remotely located and accessible within the communications network(illustrated as reference numeral 16 in FIG. 1). Regardless, thecommunications server 40 queries the ring back database 74 for theidentification sequence 70. FIG. 4 illustrates the ring back database 74as a table or map that relates personalized ring backs 18 to theidentification sequences 70. The ring back database 74 retrieves thepersonalized ring back 18 associated with the identification sequence 70received from the ring back request 72. The server-side ring back module42 then causes the communications server 40 to send or communicate thepersonalized ring back 18 to the calling party's communications device10. The communications server 40, for example, sends or routes the .mpgfile, .wav file, or picture to the communications address (e.g.,Internet Protocol address 58 or telephone number 60) associated with thecalling party's communications device 10.

As FIG. 5 illustrates, the calling party's communications device 10receives the personalized ring back 18. The ring back module 30 storesthe personalized ring back 18 in the memory (illustrated as referencenumeral 36 of FIG. 2) of the calling party's communications device 10.The ring back module 30 also associates the personalized ring back 18 tothe called party's communications address 50 (such as the called party'sInternet Protocol address 52 or called telephone number 54 illustratedin FIG. 3). The ring back module 30 may maintain or store anaddress-to-ring back database 80 in the memory 36 of the calling party'scommunications device 10. FIG. 5 illustrates the address-to-ring tonedatabase 80 as a table that relates or maps the personalized ring back18 to the called party's communications address 50. When the callingparty initiates or sends a subsequent communication to the called party,the ring back module 30 queries the address-to-ring tone database 80 forthe recipient's communications address 50. The ring back module 30retrieves the personalized ring back 18 that corresponds to therecipient's communications address 50. The calling party'scommunications device 10 then audibly and/or visually presents thepersonalized ring back 18 that corresponds to the recipient'scommunications address 50. The personalized ring back 18 alerts thecalling/sending party that the called/recipient party's communicationsdevice 14 is ringing, vibrating, or otherwise alerting to a thesubsequent communication.

FIGS. 6 and 7 are schematics illustrating a telephony ring back,according to exemplary embodiments. Here the calling party'scommunications device 10 places a telephone or Voice-over InternetProtocol call 90 to the called party's communications device 14. Thecall 90 routes and terminates to the communications address 50associated with the called party's communications device 14. Thecommunications address 50 may be the called party's Internet Protocoladdress 52 or called telephone number 54, as illustrated in FIG. 3. Asthe calling party and the called party conduct the call 90 (orVoice-over Internet Protocol data session), the called party'scommunications device 14 sends the identification sequence 70 to thecalling party's communications device 10. The identification sequence 70may be sent as a data message, a burst of data, or dual-tone modalfrequencies during the call or data session. However the identificationsequence 70 is sent, the ring back module 30 receives or detects theidentification sequence 70. The ring back module 30 stores theidentification sequence 70 in the memory (illustrated as referencenumeral 36 in FIG. 2) of the calling party's communications device 10.The calling party and the called party continue to converse until thecall 90 ends.

As FIG. 7 illustrates, the ring back module 30 detects (or is notifiedof) a termination 92 of the call 90. When the calling party and/or thecalled party end the call 90 (such as by going on-hook or terminating asession), the ring back module 30 is informed of the end or termination92 of the telephone or Voice-over Internet Protocol call 90. The ringback module 30 causes a subsequent, second call 94 to be placed to thecommunications server 40. The second call 94, for example, may be to atoll-free number associated with the communications server 40. Thesecond call 94 may even require a fee per call or per minute.Regardless, during the second call 94, the ring back module 30 causesthe calling party's communications device 10 to send, play, or presentthe identification sequence 70. The identification sequence 70, forexample, may be sent as data or dual-tone modal frequencies that aredetectable by the server-side ring back module 42. When the server-sidering back module 42 receives the identification sequence 70, theserver-side ring back module 42 queries the ring back database 74 forthe identification sequence 70. The ring back database 74 retrieves thepersonalized ring back 18 associated with the identification sequence70. The server-side ring back module 42 then, at some time, causes thecommunications server 40 to send or communicate the personalized ringback 18 to the calling party's communications device 10. Thecommunications server 40, for example, may send personalized ring back18 during the second call 94 to the calling party's communicationsdevice 10. The ring back module 30 stores the personalized ring back 18in the memory 36 of the calling party's communications device 10. Thering back module 30 also creates an entry in the address-to-ring tonedatabase 80 and associates the personalized ring back 18 to the calledparty's communications address 50 (as FIG. 5 illustrated). When thecalling party makes another, subsequent call to the called party'scommunications device 14, the ring back module 30 queries theaddress-to-ring back database 80 for the personalized ring back 18 thatcorresponds to the called party's communications address 50. Thepersonalized ring back 18 alerts the calling party that the calledparty's communications device 14 is ringing, vibrating, or otherwisealerting to the call.

FIG. 8 is another schematic illustrating the telephony ring back,according to exemplary embodiments. Much of FIG. 8 is similar to FIGS. 6and 7 and, so, only briefly explained. The calling party'scommunications device 10 places the first call 90 to the called party'scommunications device 14. As the calling party and the called partyconduct the first call 90, the called party's communications device 14sends the identification sequence 70 to the calling party'scommunications device 10. The identification sequence 70 is stored inthe memory (illustrated as reference numeral 36 in FIG. 2) of thecalling party's communications device 10. When the call 90 ends, thering back module 30 causes the subsequent, second call 94 to be placedto the communications server 40. During the second call 94, the ringback module 30 causes the calling party's communications device 10 tosend, play, or present the identification sequence 70. The server-sidering back module 42 receives the identification sequence 70 and queriesthe ring back database 74 for the identification sequence 70. Theserver-side ring back module 42 retrieves the personalized ring back 18associated with the identification sequence 70.

Here, though, the calling party's communications device 10 records thepersonalized ring back 18. During the established second call 94 betweenthe calling party's communications device 10 and the communicationsserver 40, the server-side ring back module 42 sends a command 100 tothe calling party's communications device 10. The command 100 may bedata, a message, or dual-tone multi-frequencies that are recognized ordetectable by the ring back module 30. The command 100 causes the ringback module 30 to instruct the calling party's communications device 10to enter a recording mode 102 of operation. When the recording mode 102of operation is entered, the ring back module 30 causes the callingparty's communications device 10 to send a confirmation 104 during theestablished second call 94 between the calling party's communicationsdevice 10 and the communications server 40. The confirmation 104 may bedata or one or more dual-tone multi-frequencies that confirm the callingparty's communications device 10 has entered or begun the recording mode102 of operation. When the server-side ring back module 42 receives theconfirmation 104, the server-side ring back module 42 causes thecommunications server 40 to begin streaming or playing the personalizedring back 18. The ring back module 30 in the calling party'scommunications device 10 then causes the processor (illustrated asreference numeral 38 in FIG. 2) to store or record the personalized ringback 18 to the memory 36 of the calling party's communications device10. The ring back module 30 also associates the personalized ring back18 to the called party's communications address 50 in theaddress-to-ring back database 80. When later calls are made to the samecalled party's communications device 14, the ring back module 30 queriesthe address-to-ring back database 80 for the personalized ring back 18that corresponds to the called party's communications address 50. Thepersonalized ring back 18 is retrieved and played or presented to thecalling party to indicate that the call is being established.

Calls to the communications server 40 may be inconvenient. As explainedabove, when the ring back module 30 obtains the identification sequence70, the ring back module 30 may call the communications server 40 toobtain the corresponding personalized ring back 18. The ring back module30, for example, may immediately place the subsequent, second call 94 assoon as possible after either the calling party and/or the called partyend the first call 90. If the subsequent, second call 94 is immediatelyplaced to the communications server 40, though, the user may beprevented or delayed from making calls until the personalized ring back18 is retrieved. Congestion within the communications network 16 mayalso prolong the subsequent, second call 94 to the communications server40, thus further frustrating the user. The calling party, in otherwords, may have an unacceptable wait time before the personalized ringback 18 is received or recorded.

The ring back module 30, then, may be configured to make calls to thecommunications server 40. A user, for example, may configure the ringback module 30 to only or preferably call the communications server 40during off-hours when the user is sleeping or less likely to use thecalling party's communications device 10. The user, of course, mayconfigure the ring back module 30 to call the communications server 40immediately after the identification sequence 70 is received. The usermay also configure the ring back module 30 to wait a predetermined timebefore calling the communications server 40. That is, after the ringback module 30 receives the identification sequence 70 and when thecalling party and the called party end the first call 90, the ring backmodule 30 initializes or sets a countdown timer. When the countdowntimer expires, the ring back module 30 then initiates the second call 94to the communications server 40 to obtain the personalized ring back 18.

Multiple personalized ring backs may also be “batch” delivered. Becausethe ring back module 30 may be configurable, the user may desire thatall personalized ring backs are obtained during a single call to thecommunications server 40. That is, as the calling party makes multiplecalls throughout a day, for example, numerous called parties may specifypersonalized ring backs. As the ring back module 30 receives theidentification sequence 70 for each corresponding called party, the ringback module 30 sequentially stores the identification sequences inmemory. Then, perhaps during off-hours, the ring back module 30 theninitiates the second call 94 to the communications server 40. The ringback module 30 sends all the identification sequences 70 received andstored during the day (or some other configurable time period). During asingle call to the communications server 40, then, the server-side ringback module 42 retrieves all the corresponding personalized ring backs.The ring back module 30, for example, may serially transmit orcommunicate a string of identification sequences, with each individualidentification sequence 70 corresponding to a different called party'spersonalized ring back. When the second call 94 to the communicationsserver 40 is established, the personalized ring backs 18 may then bebatch or serially communicated to the calling party's communicationsdevice 10. The ring back module 30 receives and/or records the multiplepersonalized ring backs, and each personalized ring back 18 isassociated to the corresponding called party's communications address 50in the address-to-ring tone database 80.

FIG. 9 illustrates another operating environment, according to exemplaryembodiments. Here the ring back module 30 and the server-side ring backmodule 42 may interface with a Public Switched Telephone Network 120 andwith a distributed computing network 122 (such as the Internet orlocal-area network). As those of ordinary skill in the art understand,this operating environment may utilize a packet protocol, such as theSession Initiation Protocol (SIP). This operating environment may alsoutilize voice service protocols, triggers, and/or operations that allowthe Public Switched Telephone Network 120 and the distributed computingnetwork 122 to interoperate. The communications server 40, for example,may interface with a packet-based “softswitch” that uses softwarecontrol to provide voice, data, and video services by dynamicallychanging its connection data rates and protocols types. Thecommunications server 40 may alternatively or additionally includeAdvanced Intelligent Network (AIN) componentry. This operatingenvironment, however, is well understood in the art and will not befurther described. If a reader desires a more detailed explanation, thereader is directed to U.S. Pat. No. 5,430,719 issued to Weisser (Jul. 4,1995) and to U.S. Pat. No. 5,917,817 issued to Dunn et al. (Jun. 29,1999.

FIGS. 10-11 are schematics illustrating still more exemplaryembodiments. FIG. 10 is a generic block diagram illustrating the ringback module 30, and/or the server-side ring back module 42, may operatewithin a processor-controlled device 130. The ring back module 30 and/orthe server-side ring back module 42 may be stored in a memory subsystemof the processor-controlled device 130. One or more processorscommunicate with the memory subsystem and execute the ring back module30 and/or the server-side ring back module 42. Because theprocessor-controlled device 130 illustrated in FIG. 10 is well-known tothose of ordinary skill in the art, no detailed explanation is needed.

FIG. 11 illustrates that the ring back module 30, and/or the server-sidering back module 42, may also entirely or partially operate withinvarious other communications devices 140. As FIG. 11 shows, the ringback module 30 and/or the server-side ring back module 42 may operate ina personal digital assistant (PDA) 142, a Global Positioning System(GPS) device 144, an interactive television 146, an Internet Protocol(IP) phone 148, a pager 150, a cellular/satellite phone 152, or anycomputer system and/or communications device utilizing a digital signalprocessor (DSP) 154. The calling party's communications device 10,and/or the called party's communications device 14, may also includewatches, radios, vehicle electronics, clocks, printers, gateways, andother apparatuses and systems.

FIGS. 12-14 are schematics further illustrating various communicationsdevices for presenting ring backs, according to exemplary embodiments.FIG. 12 is a block diagram of a Subscriber Identity Module 200, whileFIGS. 13 and 14 illustrate, respectively, the Subscriber Identity Module200 embodied in a plug 202 and the Subscriber Identity Module 200embodied in a card 204. As those of ordinary skill in the art recognize,the Subscriber Identity Module 200 may be used in conjunction with manycommunications devices (such as those illustrated in FIGS. 1-11). TheSubscriber Identity Module 200 stores user information (such as theuser's International Mobile Subscriber Identity, the user's K_(i)number, and other user information) and any portion of the ring backmodule 30. As those of ordinary skill in the art also recognize, theplug 202 and the card 204 each interfaces with the communicationsdevice. While exemplary embodiments are applicable to any standard, somesuch standards are GSM Standards 2.17 and 11.11 and ISO Standard 7816,with each incorporated herein by reference. The GSM Standard 2.17 isformally known as “European digital cellular telecommunications system(Phase 1); Subscriber Identity Modules, Functional Characteristics (GSM02.17 V3.2.0 (1995-01)).” The GSM Standard 11.11 is formally known as“Digital cellular telecommunications system (Phase 2+) (GSM);Specification of the Subscriber Identity Module—Mobile Equipment(Subscriber Identity Module—ME) interface (GSM 11.11 V5.3.0 (1996-07)).”Both GSM standards are available from the European TelecommunicationStandards Institute (650 route des Lucioles, 06921 Sophia-AntipolisCedex, FRANCE, Tel.: +33 (0)4 92 94 42 00, Fax: +33 (0)4 93 65 47 16,www.etsi.org). The ISO Standard 7816 is formally known as “Informationtechnology—Identification cards—Integrated circuit(s) cards withcontacts,” and the standard is available from the InternationalOrganization for Standardization (ISO) (1, rue de Varembé, Case, postale56CH-1211 Geneva 20, Switzerland, Telephone +41 22 749 01 11, Telefax+41 22 733 34 30, www.iso.org).

FIG. 12 is a block diagram of the Subscriber Identity Module 200,whether embodied as the plug 202 of FIG. 13 or as the card 204 of FIG.14. Here the Subscriber Identity Module 200 comprises a microprocessor206 (μP) communicating with memory modules 208 via a data bus 210. Thememory modules 208 may include Read Only Memory (ROM) 212, Random AccessMemory (RAM) and/or flash memory 214, and ElectricallyErasable-Programmable Read Only Memory (EEPROM) 216. The SubscriberIdentity Module 200 stores some or all of the ring back module 30 in oneor more of the memory modules 208. FIG. 12 shows the ring back module 30residing in the Erasable-Programmable Read Only Memory 216, yet the ringback module 30 could alternatively or additionally reside in the ReadOnly Memory 212 and/or the Random Access/Flash Memory 214. AnInput/Output module 218 handles communication between the SubscriberIdentity Module 200 and the communications device. Because SubscriberIdentity Modules are well known in the art, this patent will not furtherdiscuss the operation and the physical/memory structure of theSubscriber Identity Module 200. If, however, the reader desires moreinformation on the Subscriber Identity Module, the reader is directed tothe following sources: LAWRENCE HARTE et al., GSM SUPERPHONES 99-100,113-14 (1999); SIEGMUND REDL et al., GSM AND PERSONAL COMMUNICATIONSHANDBOOK 303-69 (1998); and JOACHIM TISAL, GSM CELLULAR RADIO TELEPHONY99-130 (1997), with each incorporated herein by reference.

FIG. 15 is a schematic further illustrating various communicationsdevices for presenting ring backs, according to exemplary embodiments.FIG. 15 is a block diagram of another communications device 250utilizing the ring back module 30. Here the communications device 250comprises a radio transceiver unit 252, an antenna 254, a digitalbaseband chipset 256, and a man/machine interface (MMI) 258. Thetransceiver unit 252 includes transmitter circuitry 260 and receivercircuitry 262 for receiving and transmitting radio-frequency (RF)signals. The transceiver unit 252 couples to the antenna 254 forconverting electrical current to and from electromagnetic waves. Thedigital baseband chipset 256 contains a digital signal processor (DSP)264 and performs signal processing functions for audio (voice) signalsand RF signals. As FIG. 15 shows, the digital baseband chipset 256 mayalso include an on-board microprocessor 266 that interacts with theman/machine interface (MMI) 258. The man/machine interface (MMI) 258 maycomprise a display device 268, a keypad 270, and the Subscriber IdentityModule 200. The on-board microprocessor 266 may perform TDMA, CDMA, GSMor other protocol functions and control functions for the radiocircuitry 260 and 262, for the display device 268, and for the keypad270. The on-board microprocessor 266 may also interface with theSubscriber Identity Module 200 and with the ring back module 30. Becausethe functional architecture of the communications device 250 is wellknown to those of ordinary skill in the art, the communications device250 will not be further discussed. If the reader desires a more detailedexplanation, the reader is invited to consult the following sources:LAWRENCE HARTE et al., GSM SUPERPHONES 105-120 (1999); SIEGMUND REDL etal., GSM AND PERSONAL COMMUNICATIONS HANDBOOK 389-474 (1998); andJOACHIM TISAL, GSM CELLULAR RADIO TELEPHONY 99-130 (1997).

Exemplary embodiments may be applied to any signaling standard. As thoseof ordinary skill in the art recognize, FIGS. 12-15 may illustrate aGlobal System for Mobile (GSM) communications device. That is, thecommunications device may utilize the Global System for Mobile (GSM)communications signaling standard. Those of ordinary skill in the art,however, also recognize that exemplary embodiments are equallyapplicable to any communications device utilizing the Time DivisionMultiple Access signaling standard, the Code Division Multiple Accesssignaling standard, the “dual-mode” GSM-ANSI Interoperability Team(GAIT) signaling standard, or any variant of the GSM/CDMA/TDMA signalingstandard. Exemplary embodiments may also be applied to other standards,such as the I.E.E.E. 802 family of standards.

FIG. 16 is another schematic illustrating this ring back service,according to exemplary embodiments. FIG. 16 illustrates a graphical userinterface 300 that maybe displayed by the called party's communicationsdevice 14. The graphical user interface 300 allows the called party toselect the personalized ring back 18 that is presented to the callingparty. The graphical user interface 300 may provide a selection of ringbacks to the called party. The called party may use a keypad 302 orother control to scroll through the graphical user interface 300 and toselect the desired personalized ring back 18. The called party may thenassociate the calling party's communications address with the desiredpersonalized ring back 18. The association may even be automaticallyperformed by the ring back module 30, such as when a calling number orInternet Protocol address is received with an incoming call or incomingcommunication. Once the called party selects the desired personalizedring back 18, the ring back module 30 assigns the identificationsequence 70 to the personalized ring back 18. The identificationsequence 70 may be a random or sequential alphanumeric combination thatis chosen by the ring back module 30. The ring back module 30 mayperform a survey or check of all identification sequences to ensure thatthe calling number or Internet Protocol address is not assigned orassociated with multiple ring backs. Once the identification sequence 70is verified, the ring back module 30 will then send the identificationsequence 70 upon receipt or indication of subsequent calls orcommunications from the same calling number or Internet Protocol address(as the above paragraphs explained).

FIG. 17 is a schematic illustrating a network-centric ring back service,according to exemplary embodiments. Here the server-side ring backmodule 42, operating in the communications server 40, providesnetwork-based control of the ring back service. When the calling party'scommunications device 10 sends a communication or places a call 350 tothe called party's communications device 14, the server-side ring backmodule 42 is notified of the call or communication 350. The call orcommunication 350, for example, may be routed to or through thecommunications server 40. The communications server 40, alternatively oradditionally, may be notified of the call or communication 350 bynetwork signaling or messaging. When the server-side ring back module 42learns of the call or communication 350, for example, the server-sidering back module 42 is also informed of the calling number and thecalled number. If an electronic communication is sent, the server-sidering back module 42 is informed of the sender's Internet Protocoladdress and the recipient's Internet Protocol address. Regardless, theserver-side ring back module 42 is notified of each party'scommunications address.

The server-side ring back module 42 then selects the identificationsequence 70. The server-side ring back module 42 queries a server-sidering back database 400 for each party's communications address. Theserver-side ring back database 400 maps or relates a sender/callercommunications address and a recipient/callee communications address tothe associated identification sequence 70. As the communicating partiesconverse or conduct a session, the server-side ring back module 42causes the communications server 40 to interject and communicate thecorresponding identification sequence 70 (e.g., detectable data, tones,or messages, as the above paragraphs explained) to the calling party'scommunications device 10. The calling party's communications device 10may then make a subsequent call or communication to the communicationsserver 40 and send the identification sequence 70. The server-side ringback module 42 obtains the identification sequence 70, retrieves theassociated ring back 18, and sends the personalized ring back 18 to thecalling party's communications device 10.

Network selection of the ring back 18 is also possible. The called partysubscriber might provide a list of approved ring backs. The list couldinclude any content, such as music, movies, pictures, streamingaudio/video, or other content. The subscriber could then let theserver-side ring back module 42 select the ring back on behalf of thesubscriber. That is, when the called party subscriber receives acommunication (such as an email or a telephone call), the calling partywould experience the ring back 18 selected from the list. Theserver-side ring back module 42 could use any method of selecting thering back 18 from the approved list. The ring server-side ring backmodule 42, for example, could randomly select from the list, or theserver-side ring back module 42 could sequentially work through the listwith each successive communication. However the ring back 18 isselected, the server-side ring back module 42 may select the ring back18 on behalf of the subscriber.

Exemplary embodiments may also be applied to an Internet Protocolenvironment. Exemplary embodiments may analyze a header portion and/or apayload portion of one or more packets of data. The header portionand/or the payload portion may include data representing a callingnumber, a called number, a sender's Internet Protocol address, and/or arecipient's Internet Protocol address. Exemplary embodiments may thenuse this packetized data to retrieve the identification sequence 70and/or the personalized ring back 18, as the above paragraphs explained.

FIG. 18 is a flowchart illustrating a method of providing thepersonalized ring back 18, according to exemplary embodiments. Agraphical user interface is stored in memory (Block 500). The graphicaluser interface may be stored in the memory of a computer (such as thecomputer server 22), and the graphical user interface isaccessed/downloaded via the Internet. The graphical user interface mayadditionally or alternatively be locally stored in the memory of acommunications device. The graphical user interface presents a selectionof ring backs to the subscriber. The selection of ring backs allows thesubscriber to specify the ring back to be presented on the callingparty's communications device 10. The subscriber may be allowed topreview a ring back (Block 502), thus allowing the subscriber to see,hear, feel, and/or otherwise experience the ring back before selection.The subscriber's selection of a ring back is accepted (Block 504), andthe subscriber is allowed to associate the ring back to a telephonenumber or Internet Protocol address of the calling party (Block 506).The selected ring back is processed (Block 508). The ring back ispresented to a calling party or sender to indicate the subscriber'scommunications device is alerting of an incoming communication (Block510).

FIG. 19 is another flowchart illustrating another method of providingthe personalized ring back 18, according to exemplary embodiments. Afirst call is placed to a called number (Block 600). An identificationsequence 70 is received during the first call (Block 602). A second callis placed to a server when the first call is completed (Block 604). Anidentification sequence 70 is sent to the server during the second call(Block 606). The personalized ring back 18 is received during the secondcall (Block 608) and stored (Block 610). When subsequent calls are madeto the called number, the personalized ring back is retrieved frommemory and presented to the calling party (Block 612).

The terms “processed,” “process,” “processing,” and variants, as usedherein, encompass any event from the time the calling party'scommunications device initiates a communication to the termination ofthe communication. The terms “processed,” “process,” “processing,” andvariants include storing the ring back in memory, routing a voice path,signaling setup, and intelligence queries (e.g., Local NumberPortability queries, queries to retrieve Calling/Called Name/Numberinformation, AIN queries, and standard signaling messages to determinecall routing paths). The terms “processed,” “process,” “processing,” andvariants also include monitoring an established telephone call forpossible DTMF entry, switch hook flash, other events that indicate aparty on the telephone call has requested something, and delivery ofcall waiting tones and data. The terms “processed,” “process,”“processing,” and variants also include identification of packets, ofpacket headers, and of the payload contents of packets. The terms“processed,” “process,” “processing,” and variants include decipheringthe payload contents of a packet and acting on those payload contents.The terms “processed,” “process,” “processing,” and variants alsoinclude storing ring back selections in memory, retrieving those ringback selections, and communicating those ring back selections to thecalling party. The terms “processed,” “process,” “processing,” andvariants, however, also encompass billing activities and measurements ata switch or any other network element.

Censorship is also permissible. The subscriber to this service canspecify the ring back to be presented on a calling party'scommunications device. The calling party, however, may choose to blockor censor the called party's selected ring back. The calling party maynot approve of certain content for the ring back. The calling party maydislike some ring backs. The calling party, for example, may disapproveof lyrics, scenes, or other content in the ring back. This inventionwould also provide the calling party an opportunity to block or censorthe called party's selected ring back. The calling party may maintain aprofile in the ring back database 24. When the called party's ring backis retrieved, the ring back module 30 could cross-reference the calledparty's ring back to the calling party's list of approved/censored/blockring backs. If a match is found, the ring back module 30 wouldapprove/decline the selected ring back. The calling party's profile mayspecify a default ring back to be presented to the calling party, in theevent the subscriber's selected ring back is censored/blocked. Thecalling party's profile may even demand a mandatory ring back to bepresented to the calling party, regardless of the subscriber's selectedring back.

Exemplary embodiments may also be applied to busy signals. As mostpeople know, when a telephone line is dedicated for a phone call and/ora data session, another caller hears a busy signal. This busy signalindicates the called party's line is engaged in a telephone/data session(e.g., Internet Call Waiting). Exemplary embodiments could also beapplied to customizable busy signals. That is, the called party usesthis service to determine the type of busy signal heard by the callingparty. The calling party might hear a favorite song, view a picture,view portions of a movie, or see other graphics. The subscriber mighteven select personal pictures, self-composed music, and/or streamedaudio and/or video content (such as radio, stock quotes, news, weather,and/or advertisements). The called party might also specify a busysignal by electronic calendar entries, such as the day of the week, thetime of day, and/or appointments in the calendar. The called partysubscriber may even associate particular busy signals to particularcalling parties, thus providing a variety of personalized busy signals.

The ring back module (shown as reference numeral 20 in FIGS. 2-17) maybe physically embodied on or in a computer-readable medium. Thiscomputer-readable medium may include CD-ROM, DVD, tape, cassette, disk,memory card, and large-capacity disk (such as IOMEGA®, ZIP®, JAZZ®, andother large-capacity memory products (IOMEGA®, ZIP®, and JAZZ® areregistered trademarks of Iomega Corporation, 1501 W. Iomega Way, Roy,Utah 84067, 801.332.1000, www.iomega.com). This computer-readablemedium, or media, could be distributed to end-users, licensees, andassignees. These types of computer-readable media, and other types notmention here but considered within the scope of the present invention,allow the ring back module to be easily disseminated. A computer programproduct for providing ring backs to a calling party comprises thecomputer-readable medium and processor-readable instructions forperforming a method of providing ring backs, as the above paragraphsexplained.

The ring back module may be physically embodied on or in any addressable(e.g., HTTP, I.E.E.E. 802.11, Wireless Application Protocol (WAP))wireless device capable of presenting an IP address. Examples couldinclude a computer, a wireless personal digital assistant (PDA), anInternet Protocol mobile phone, or a wireless pager.

Exemplary embodiments may be applied regardless of networkingenvironment. The communications network 16 may be a cable networkoperating in the radio-frequency domain and/or the Internet Protocol(IP) domain. The communications network 16, however, may also include adistributed computing network, such as the Internet (sometimesalternatively known as the “World Wide Web”), an intranet, a local-areanetwork (LAN), and/or a wide-area network (WAN). The communicationsnetwork 16 may include coaxial cables, copper wires, fiber optic lines,and/or hybrid-coaxial lines. The communications network 16 may eveninclude wireless portions utilizing any portion of the electromagneticspectrum and any signaling standard (such as the I.E.E.E. 802 family ofstandards, GSM/CDMA/TDMA or any cellular standard, and/or the ISM band).The communications network 16 may even include powerline portions, inwhich signals are communicated via electrical wiring. The conceptsdescribed herein may be applied to any wireless/wireline communicationsnetwork, regardless of physical componentry, physical configuration, orcommunications standard(s).

While exemplary embodiments have been described with respect to variousfeatures, aspects, and embodiments, those skilled and unskilled in theart will recognize exemplary embodiments are not so limited. Othervariations, modifications, and alternative embodiments may be madewithout departing from the spirit and scope of the claims.

1. A method, comprising: receiving an identification sequence during acall to a called number; retrieving a ring back associated with theidentification sequence; and presenting the ring back during asubsequent call to the called number to indicate the called number isringing.
 2. The method according to claim 1, further comprising callinga server when the call is completed.
 3. The method according to claim 2,further comprising sending the identification sequence to the server. 4.The method according to claim 3, further comprising associating theidentification sequence to the ring back.
 5. The method according toclaim 1, further comprising further comprising calling the called numberto establish the subsequent call.
 6. The method according to claim 1,further comprising associating the ring back to the called number.
 7. Asystem, comprising: a processor executing code stored in memory thatcauses the processor to: place a first call to a called number; receive,during the first call, an identification sequence; place a second callto a server when the first call is completed; send the identificationsequence to the server during the second call; receive a ring backassociated with the identification sequence; and present the ring backduring a subsequent call to the called number to indicate the callednumber is ringing.
 8. The system according to claim 1, wherein the codefurther causes the processor to receive a command from the server torecord the ring back.
 9. The system according to claim 1, wherein thecode further causes the processor to store the ring back in the memory.10. The system according to claim 1, wherein the code further causes theprocessor to retrieve the ring back from the memory for the subsequentcall to the called number.
 11. The system according to claim 1, whereinthe code further causes the processor to receive the identificationsequence as a burst of data during the first call to the called number.12. The system according to claim 1, wherein the code further causes theprocessor to receive the ring back during the second call to the server.13. The system according to claim 1, wherein the code further causes theprocessor to record the ring back to the memory.
 14. The systemaccording to claim 1, wherein the code further causes the processor toproduce a default ring back that indicates the called number is ringing.15. A computer readable medium storing processor-executable instructionsfor performing a method, the method comprising: placing a first call toa called number; receiving, during the first call, an identificationsequence; placing a second call to a server during off-hours; sendingthe identification sequence to the server during the second call;receiving a ring back associated with the identification sequence; andpresenting the ring back during a subsequent call to the called numberto indicate the called number is ringing.
 16. The computer readablemedium according to claim 15, further comprising instructions forreceiving a command from the server to record the ring back.
 17. Thecomputer readable medium according to claim 15, further comprisinginstructions for storing the ring back in memory.
 18. The computerreadable medium according to claim 15, further comprising instructionsfor retrieving the ring back from memory for the subsequent call to thecalled number.
 19. The system according to claim 1, wherein the codefurther causes the processor to receive the identification sequence as aburst of data during the first call to the called number.
 20. Thecomputer readable medium according to claim 15, further comprisinginstructions for receiving the ring back during the second call to theserver.